Datacenter power management system

ABSTRACT

Various methods and systems for implementing resource management for an infrastructure are provided. Resource management includes datacenter byproduct management interfaces, datacenter power management, datacenter operations optimization and infrastructure resource management. Resource management facilitates using and distributing physical resources, including incidental physical resources that are generated during operation of an infrastructure, based on a minimum threshold reserve of the physical resource associated with the operating the infrastructure. Resource management can include controlling an amount of the physical resource that is generated and an amount the physical resource that is reserved. The minimum threshold reserve in combination with the control over generating and reserving the physical resource help identify an allocable amount of the physical resource. Physical resources of an infrastructure are quantified to support resource management. Quantifying physical resources is associated with devices of the infrastructure and requests for physical resources in the infrastructure to perform different types of operations.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related by subject matter to the inventionsdisclosed in the following commonly assigned applications filed on evendate herewith: U.S. application Ser. No. 15/199,959, entitled“DATACENTER BYPRODUCT MANAGEMENT INTERFACE SYSTEM” U.S. application Ser.No. 15/199,963, entitled “DATACENTER OPERATIONS OPTIMIZATION SYSTEM” andU.S. application Ser. No. 15/199,964, entitled “INFRASTRUCTURE RESOURCEMANAGEMENT SYSTEM.” Each of the aforementioned applications is hereinincorporated by reference in its entirety.

SUMMARY

Embodiments described herein provide methods and systems forimplementing resource management for an infrastructure (e.g., adatacenter infrastructure). Resource management includes datacenterbyproduct management interfaces, datacenter power management, datacenteroperations optimization and infrastructure resource management. At ahigh level, resource management facilitates using physical resources,including incidental physical resources, that are generated duringoperation of an infrastructure based on a minimum threshold reserve ofthe physical resource associated with the operating the infrastructure.Resource management can include controlling an amount of the physicalresource that is generated and an amount the physical resource that isreserved. The minimum threshold reserve in combination with the controlover generating and reserving the physical resource help identify anallocable amount of the physical resource.

A resource management system facilitates defining and allocatingresources associated with the infrastructure. In particular, theresource management system processes resources and requests forresources based on a resource management framework built on ApplicationProgramming Interfaces (API) and resource management components.Physical resources of an infrastructure can be quantified to supportresource management. Quantifying physical resources can be associatedwith devices of the infrastructure and/or requests for physicalresources in the infrastructure to perform operations. Requests forphysical resources of the infrastructure can be received from externalentities that need the physical resources.

In one embodiment, an instance (e.g., device instance) is a computedrepresentation of an infrastructure device in relation to a physicalresource (e.g., power, water, carbon dioxide and heat) and a reserve ofthe physical resource, where the instance supports determining allocableunits of the physical resource. In another embodiment, an instance(e.g., operation instance) represents an amount of a physical resourceneeded to perform an anticipated operation; the instance is also used todetermine allocable units of the physical resource. The resourcemanagement system can monitor physical resources and devices usingdevice instances and allocate the physical resources based on operationinstances. As such, the resource management system can communicate anamount of allocated units for a request of a physical resource based onan amount of units of the physical resource that is being generated andan amount of the physical resource that is reserved.

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the detaileddescription. This summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used in isolation as an aid in determining the scope of the claimedsubject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments are described in detail below with reference to the attacheddrawing figures, wherein:

FIG. 1 is a block diagram of an exemplary distributed computingenvironment in which embodiments described herein may be employed;

FIG. 2 is a flow diagram showing an exemplary method for providingresource management, in accordance with embodiments described herein;

FIG. 3 is a flow diagram showing an exemplary method for providingresource management, in accordance with embodiments described herein;

FIG. 4 is a block diagram of an exemplary distributed computingenvironment in which embodiments described herein may be employed;

FIG. 5 is a flow diagram showing an exemplary method for providingresource management, in accordance with embodiments described herein;

FIG. 6 is a flow diagram showing an exemplary method for providingresource management, in accordance with embodiments described herein;

FIG. 7 is a block diagram of an exemplary distributed computingenvironment in which embodiments described herein may be employed;

FIG. 8 is a flow diagram showing an exemplary method for providingresource management, in accordance with embodiments described herein;

FIG. 9 is a flow diagram showing an exemplary method for providingresource management, in accordance with embodiments described herein;

FIG. 10 is a block diagram of an exemplary distributed computingenvironment in which embodiments described herein may be employed;

FIG. 11 is a flow diagram showing an exemplary method for providingresource management, in accordance with embodiments described herein;

FIG. 12 is a flow diagram showing an exemplary method for providingresource management, in accordance with embodiments described herein;

FIG. 13 is a block diagram of an exemplary computing environmentsuitable for use in implementing embodiments described herein; and

FIG. 14 is a block diagram of an exemplary computing environmentsuitable for use in implementing embodiments described herein.

DETAILED DESCRIPTION

Datacenters can provide housing for computing systems and associatedcomponents. The computing systems and components can support compute andstorage operations for a variety of compute workloads and operations.Datacenters also include includes several devices or apparatus thatconsume and produce physical resources (e.g., power, water, heat andcarbon dioxide). For example, large datacenters can use a significantamount of electrical power and water and produce heat and carbondioxide.

A growing number of industries are utilizing datacenter resources, whichhas led to an ever-increasing amount of resource usage at datacentersand consequently the production of byproducts that can negatively impactthe environment. As such, a comprehensive approach for operatingdatacenters for managing the increased use of resources, in particularphysical resources, and controlling the increased production ofbyproducts can advantageously improve the operation of datacenters andreduce the negative consequences on the environment.

Embodiments described herein provide simple and efficient methods andsystems for implementing resource management (e.g., datacenter byproductmanagement interfaces, datacenter power management, datacenteroperations optimization, and infrastructure resource management) forinfrastructures. At a high level, the resource management systemprovides a system for datacenter providers to operate datacenters withoptimum efficiency, where efficient use of resources, especiallyphysical resources, in a datacenter leads to achieving maximumproductivity with minimum wasted resources. Also, the resourcemanagement system provides the capacity to leverage incidental andsometimes inevitable byproducts (i.e., physical resources as byproducts)of operating datacenter as resources in and around the datacenter. Insome cases, byproducts may previously have been considered wasteproducts of the datacenter. Nonetheless, the resource management systemcan efficiently generate, reserve, process, consume and distribute thebyproduct physical resources of the datacenter. As such, the increasedefficiency and usage of byproducts reduce the environmental impact of adatacenter operating based on the resource management system.

In operation, resource management facilitates using physical resources,including incidental physical resources, that are generated duringoperation of an infrastructure based on a minimum threshold reserve ofthe physical resource associated with the operating the infrastructure.Resource management can include controlling an amount of the physicalresource that is generated and an amount the physical resource that isreserved. The minimum threshold reserve in combination with the controlover generating and reserving the physical resource is used to identifyan allocable amount of the physical resource.

The resource management system facilitates defining and allocatingresources associated with the infrastructure. In particular, theresource management system processes resources and requests forresources based on a resource management framework built on ApplicationProgramming Interfaces (API) and resource management components.Physical resources of an infrastructure can be quantified to supportresource management. Quantifying physical resources can be associatedwith devices of the infrastructure and/or requests for physicalresources in the infrastructure to perform operations. Requests forphysical resources of the infrastructure can be received from externalentities that need the physical resources.

In one embodiment, an instance (e.g., device instance) is a computedrepresentation of an infrastructure device in relation to a physicalresource (e.g., power, water, carbon dioxide, heat) and a reserve of thephysical resource, where the instance supports determining allocableunits of the physical resource. In another embodiment, an instance(e.g., operation instance) represents an amount of a physical resourceneeded to perform an anticipated operation; the instance is also used todetermine allocable units of the physical resource. The resourcemanagement system can monitor physical resources and devices usingdevice instances and allocate the physical resources based on operationinstances.

As such, the resource management system can communicate an amount ofallocated units for a request of a physical resource based on an amountof units of the physical resource that is being generated and an amountof the physical resource that is reserved. The resource managementsystem can support different types of implementations including: adatacenter byproduct management interface system, a datacenter powermanagement system, a datacenter operations optimization system, and aninfrastructure resource management system, as discussed in more detailbelow.

Datacenter Byproduct Management System

By way of example, for illustration of a first embodiment describedherein, a datacenter can support a datacenter byproduct managementsystem. The datacenter includes several types of devices. The devicesoperate to perform functions that support operations in the datacenter.For example, servers operate to provide compute resources or storageresources and a fan operates produce a current of air for cooling thedatacenter. With the datacenter byproduct management system, datacenterdevices can further be described as byproduct devices. A byproductdevice consumes or supplies a specific byproduct—i.e., a physicalresource (e.g., power, water, carbon dioxide—CO₂, heat) of thedatacenter. The datacenter byproduct management system provides acomprehensive view of physical resources that are available at thedatacenter. Physical resources can be generated intentionally orincidentally by the datacenter devices. In either case, the physicalresource is tracked and can further be identified as an intentionallyproduced physical resource or an incidental physical resource. Forexample, an electrical device can produce electricity intentionally butgenerate heat and water incidentally. The datacenter byproductmanagement system operates to efficiently generate, reserve, use anddistribute physical resources and in particular process and utilizebyproduct physical resources that would other be regarded as waste. Thedatacenter byproduct management system can specifically rely ontechnology-based techniques for implementation of resource management.

The datacenter byproduct management system operates using an ApplicationProgramming Interface (API) that supports a protocol for performingoperations based on byproduct resources. At a high level, the API allowsthe datacenter including datacenter devices and physical resources to beexpressed in terms of operations, inputs, outputs, and underlyingclassification types for characteristics of the datacenter. The API candefine functionalities that are independent of specific implementations,allowing definitions and implementations to vary without compromisinginterfaces. The API can support representing, processing andcommunicating information associated with the physical resources.Physical resources can be generated, reserved, allocated andcommunicated based the APIs of the datacenter byproduct managementsystem. In particular, the API can define a byproduct device in relationto the physical resource and a reserve of the physical resource. Usingthe APIs and byproduct management system, a byproduct device can beidentified and classified with one or more physical resources (e.g.,power devices, water devices, CO₂ devices or heat devices). The APIsdefine units for quantifying the physical resource including ageneration capacity of units of the physical resource by the byproductdevice and reserve units of the physical resource associated with thebyproduct device.

The datacenter byproduct management system also operates based onminimum threshold limits of physical resources associated with operatingat least the datacenter. The minimum threshold limit of a physicalresource can refer to a benchmark attribute for guidance on how much ofthe physical resource is needed to operate the datacenter. A breach ofthe minimum threshold can be configured to trigger remediationoperations. The minimum threshold limit can be defined based ondatacenter processes and performance metrics for the individual andcombinations of physical resources. The minimum threshold limit of thephysical resource can also be calculated and represented based on unitsdefined in the API. The minimum threshold limit, quantified using theAPI, indicates an amount of the physical resource needed to operate thedatacenter.

In operation, a byproduct resource manager of the datacenter byproductmanagement system can receive data for a byproduct device associatedwith the datacenter. It is contemplated that the byproduct resourcemanager continuously and automatically monitors byproduct devices andgenerates and updates device instances to provide a comprehensive viewof physical resources. The byproduct resource manager can then use thedata to generate a representation (e.g., device instance) byproductdevice. In particular, a generation capacity of units of the physicalresource and reserve units of the physical resource are identified. Thedevice instance can be used to determine allocable units of the physicalresource. The byproduct resource manager can specifically communicatewith the byproduct device on an amount of units of the physical resourceto be generated and an amount resource to be reserved based on thedevice instance and the minimum threshold limit of the physicalresource.

An amount of allocated units can be identified from the allocable unitsand communicated as available for use. The amount of allocated units canbe generated based on a request having requested units of a physicalresource. A remote resource interface can communicate the request andthe byproduct resource manager can identify allocable units anddetermine allocated units for the request. In one embodiment, therequest can be used to generate an operation instance for processing therequest with the same API-based representation of the device instance.

Datacenter Power Management System

By way of example, for illustration of a second embodiment describedherein, a power management system is provided for leveraging powerdevices in a datacenter to support electrical infrastructures (e.g., apower grid). A datacenter can include several power devices (e.g.,servers, racks hardware, network devices, batteries, etc.) that consumeor supply power available at the datacenter. In one unique example, apower device can be an uninterruptable power supply (UPS) or a powergenerator. At a high level, the UPS can operate to consume power whencharging batteries in the UPS and supply power stored in the batteries.The power generator in its own right operates to generate power.

The resource management APIs can provide a representation of powerdevices in the power management system. The resource management APIs canbe configured to support representing electrical attributes associatedwith power devices and using the API representations (e.g., deviceinstances, operation instances) that include the power device data toperform resource management. Sensors associated with power devices canhelp track electrical attributes represented using the APIs. Electricalattributes can refer to measureable electrical quantities that areparameters and operational characteristics of the electrical devices.Electrical attributes can include leading factor, lagging factor,reactive power, active power factor correction, power factor penalty,frequency firming, voltage correction, inductive loads, capacitiveloads, phase correction and so on. In this regard, power device can befurther associated with a power management scheme for electricalattributes of the power device. The power management scheme supportsgenerating and reserving power based on corresponding electrical devicesand electricity processing techniques associated with the power device.Using the APIs, the UPS, the generator and other power devices can beidentified and classified as a power devices associated with power as aresource of the datacenter.

The datacenter power devices and electrical attributes can be used toshape power in that the power devices can be used to control generation,reservation, consumption, allocation and distribution of datacenterpower. For example, the power device data can be used to change thedatacenter from a lagging power factor to a leading power factor.Reactive power can be preserved and used as real power when needed. Inparticular, the scale of power usage and power devices at massivedatacenters can significantly affect power management when performedbased on the plurality of power devices in the datacenter, allowing thefractional changes in individual power devices to in the aggregatetranslate to significant results in shaping power. Shaping power,advantageously, yields lower charges from the utility companies. Thepower management systems can operate metaphorically as a shock absorberfor a corresponding power grid.

By way of background, a power grid can experience micro-deficits inpower (e.g., in the middle of the day there is more solar than in middleof night) and the fluctuation in supply and demand of power provided bya power utility provider impacts the power grid efficiency andfunctionality. The power management system can mitigate the impact ofmicro-deficits on the grid and help counter the inefficiencies of apower grid. In one example, the capacity of the datacenter to generatepower and store power can be leveraged to compensate for any power drawnaway from the datacenter. A minimum threshold limit of the power for thedatacenter can also be calculated based on units defined in the API. Theminimum threshold limit indicates an amount of power needed to operatethe datacenter. The minimum threshold limit of power can be based on aplurality of different internal and external factors. For example, anassessment of the performance of the datacenter based on workloads,operating environment, operations resources and physical resources canbe used as a benchmark for setting minimum threshold limits for physicalresources at the datacenter. A minimum threshold manager can be aportion of the resource management system that provides the thresholdlimits to be applied to resource management. It is contemplated that theAPIs provide support for representing the minimum threshold data forperforming evaluations with other representations in the resourcemanagement system. As, such, advantageously, the datacenter operates toallow for other renewable sources of energy to be part of the power gridin that the power management systems compensates for the micro-deficitsthat are common when using renewable sources of power. Further, thedatacenter operates as a peaking plant with less environment impact thantraditional peaking plants that emit greenhouse gases.

In operation, power device data can be received at a power manager andrepresented as a device instance. For example, the UPS can berepresented as a device instance having a plurality ofattributes—classification, generation capacity units of power, andreserved units of power. The device instance along with the minimumthreshold reserve of power associated with operating the datacenter canbe used to determine allocable units of power. The power manager canalso specifically instruct power devices as to an amount of units ofpower to be generated and an amount of units of power to be reserved.Generating power can be based on the power device (e.g., generator)producing power in part by transmitting power from a generation sourceto be made available for consumption via the datacenter or the powerdevice (e.g., fans, computing devices, power supplies) throttling usageof power such that an unused portion of power is made available forconsumption via the datacenter. An amount of allocated units of power,defined based on the amount of power that is being generated and theamount of units of power that is reserved can be provided for a requestand communicated to a power requesting interface.

Datacenter Operations Optimization System

By way of example, for illustration of a third embodiment describedherein, a datacenter optimization system is provided for a byproductmanagement system for a datacenter that operates in combination with aco-located operating infrastructure. A co-located infrastructure canrefer to one of the following: a power grid, an agricultural facility, amanufacturing facility, a building, and a remote datacenter. Asdiscussed above, the datacenter includes several types of devices(byproduct devices) that operate to consume or supply a specificbyproduct—i.e., a physical resource (e.g., power, water, carbondioxide—CO₂, heat) of the datacenter. The co-located operatinginfrastructure can similarly be represented using the byproductmanagement system. Using the APIs and byproduct management system, abyproduct device, in the datacenter or the co-located operatinginfrastructure can be identified and classified with one or morephysical resources (e.g., power devices, water devices, CO₂ devices orheat devices). The APIs define units for quantifying the physicalresource including a generation capacity of units of the physicalresource by the byproduct device and reserve units of the physicalresource associated with the byproduct device. A minimum threshold limitof the physical resource can also be calculated based on units definedin the API. The minimum threshold limit indicates an amount of thephysical resource needed to operate both the datacenter and theco-located operating infrastructure. The minimum threshold limit ofpower can be based on a plurality of different internal and externalfactors of the datacenter and the co-located operating infrastructure.For example, an assessment of the performance of the datacenter and theco-located infrastructure based on workloads, operating environment,operations resources and physical resources can be used as a benchmarkfor setting minimum threshold limits for physical resources at thedatacenter and the co-located infrastructure. A minimum thresholdmanager can be a portion of the datacenter operations optimizationsystem that provides the threshold limits to be applied to resourcemanagement. In this regard, the datacenter generation capacity,reserves, and minimum thresholds can be based on the combination of thedatacenter and the co-located operating infrastructure.

In operation, a byproduct resource manager can receive data for abyproduct device associated with the datacenter. The byproduct resourcemanager can then use the data to generate a representation (e.g.,instance) of the byproduct device. In particular, a generation capacityof units of the physical resource and reserve units of the physicalresource are identified. The device instance can be used to determineallocable units of the physical resource. An amount of allocated unitscan be identified from the allocable units and communicated as availablefor use.

In one embodiment, the remote resource interface is associated with asecond datacenter. The datacenter operations optimization system canprovide a compute resource manager that has access to the availabilityof compute resources at the first datacenter. In particular, theavailability of compute resource can be due to availability of physicalresources. For example, a generator at the first datacenter may beundergoing maintenance process that requires the generator to run for aperiod of time. The compute resource manager of the datacenteroperations optimizing system can identify the maintenance process as aresource management opportunity because of the additional computecapacity available at the datacenter, at least for a period when thegenerator is undergoing the maintenance run. As such, a computerworkload, based on a request for compute resources from the seconddatacenter, can be received and processed at the first datacenter onbehalf of the second data center.

Further, the byproduct resource manager and a remote resource interfacethat receives the allocated units of the physical resource (or computeresources that are based on the availability of a physical resource),can also communicate corresponding notifications. The notifications canbe communicated to start running one or more physical devices within thedatacenter and another operating infrastructure that is associated withthe remote resource interface. The notifications initiate operationprocesses for processing the amount of allocated units of the one ormore physical resources. For example, the datacenter may turn on a gridconnector to support power variability of the grid, while the power gridstarts operating power components within the grid that will use theallocated units.

Infrastructure Management System

By way of example, for illustration of a fourth embodiment describedherein, an infrastructure management system is provided. Theinfrastructure management system operates with the APIs defined aboveand also the framework of defining a minimum threshold of a physicalresource needed to operate the infrastructure. In this regard, theinfrastructure management system receives infrastructure device data andgenerates device instances for the devices to support resourcemanagement functionality. In addition, the infrastructure managementsystem, in particular, defines a representation (e.g., an operationinstance) of an anticipated operation of a device in the infrastructure.The operation instance includes requested physical resource units thatindicate an amount of a physical resource that is needed in anticipationof an infrastructure device operation. For example, the infrastructuredevice is an electrical appliance (e.g., manufacturing machinery,refrigerator, etc.) that is associated with the infrastructure (e.g.,manufacturing plant, building facility etc.) and one or more additionalinfrastructure devices in the infrastructure are computing deviceswithin the infrastructure. The anticipated need of the electricalappliance and a minimum threshold reserve of power that is associatedwith operating the one or more additional infrastructure devices areused to determine an amount of units of power to be generated and anamount of units power to be reserved.

The device instances can be used to determine allocable units of thephysical resource. An identified amount of allocable units and adetermination of allocated units of the physical resource can be basedon an amount of units of the physical resource that is being generatedand an amount of units of the physical resource that is reserved.Operating instructions including the amount of allocated units of thephysical resource for the operational instance are then communicated tothe infrastructure device. For example, the amount of allocated units ofthe physical resource is communicated to the electrical appliance andinstructions to begin the anticipated electrical appliance operation.

The resource management system, implemented as byproduct managementinterfaces, datacenter power management, datacenter operationsoptimization and infrastructure resource management provides a systemfor datacenter providers to operate datacenters with optimum efficiency,where efficient use of resources in a datacenter leads to achievingmaximum productivity with minimum wasted resources. Also the resourcemanagement system provides that capacity to utilize byproduct physicalresources and incidental and unintended byproduct physical resources ofoperating datacenter as resources in and around the datacenter.

Resource Management System

With reference to FIG. 1, embodiments of the present disclosure can bediscussed with reference to an exemplary resource management system 100that is an operating environment for implementing functionalitydescribed herein. The resource management system 100 includes abyproduct resource manager 110, a plurality of devices 120 (120A, 120B,120C and 120D) and a remote resource interface 130. The byproductresource manager 110 monitors a plurality of byproducts 112 (112A, 112B,112C and 112D) of the plurality of devices 120. The byproduct resourcemanager 110 also includes an Application Programming Interface 114 and abyproduct threshold manager 116.

With continued reference to FIG. 1, the resource management system 100facilitates defining and allocating resources associated with thedatacenter. The resource management system 100 includes the byproductresource manager 110 that processes physical resources and requests forphysical resources. The byproduct resource manager 110 operates based ona resource management framework and the components associated with thebyproduct resource manager.

The resource management system includes the plurality of byproductdevices 102. A byproduct device can operate to perform operations in thedatacenter 120A to support functionality of the datacenter. Thebyproduct device can also be associated with physical resources,referred to as byproduct device physical resources. As used herein, thebyproduct can be associated with physical resources that areintentionally or incidentally generated. For example, byproduct device120A is associated with physical resources 126A, 126B and 126C,byproduct device 120B is associated with physical resources 126A and126B, and byproduct device 120C is associated with physical resources126A and 126B and byproduct device 120D is associated with physicalresource 120A, 126B, 126C and 126D. The byproduct devices operate toconsumer or supply the associated physical resources. Byproduct devicescan also operate to conserve physical resources. Byproduct devices cancommunicate byproduct device data (e.g., byproduct device data 122) tosupport functionality described herein. The byproduct device data can begenerated based on sensors or other data tracking mechanisms associatedwith byproduct devices. The data that is measured and communicated atbyproduct device can be constructed and communicated based on APIs ofthe resource management system 100.

The resource management system 100 includes the remote resourceinterface 130. The remote resource interface 130 can be associated witha remote resource operating environment 130A (e.g., a power grid, agreenhouse, or a manufacturing plant). The remote resource operatingenvironment 130A is associated with the remote resource interface torequest (e.g., requested units 32) units of a physical resourceavailable at the datacenter. The remote resource interface can beconfigured to access resource requirements of the remote resourceoperating environment 130A and communicate requested units of a physicalresource. The requested units 132 can be constructed and communicatedbased on APIs of the resource management system 100. Requested units ofa physical resource can be received and then used to generate anoperation instance. However, it is further contemplated that therequested unit may be constructed as operation instances at the remoteresource interfaces, in the alternative. The remote resource interface130 receives allocated units 134 of the physical resource that isrequested. The remote resource interface can communicate notificationsthat further trigger components within the remote resource operatingenvironment 130 to utilize the allocated units of the physical resource.

The byproduct resource manager 110 includes the API 114 that supports aprotocol for performing operations based on byproduct resources. The APIallows the datacenter including datacenter devices and physicalresources to be expressed in terms of operations, inputs, outputs, andunderlying classification types for characteristics of the datacenter.The API can define functionalities that are independent of specificimplementations, allowing definitions and implementations to varywithout compromising interfaces. The API can support representing,processing and communicating information associated with the physicalresources.

The byproduct resource manager 110 also includes the byproduct thresholdmanager 116. The byproduct threshold manager 116 support the resourcemanagement system 100 to operate based on minimum threshold limits ofphysical resources. The minimum threshold limit of a physical resourcecan refer to a benchmark attribute for guidance on how much of thephysical resource is needed to operate the datacenter. A breach of theminimum threshold can be configured to trigger remediation operations.For example, alarms can be triggered or the datacenter can selectivelyshut operation of non-essential devices to conserve the physicalresources. Other variations and combination of remediation operationsare contemplated with embodiments described herein. The minimumthreshold limit can be defined based on datacenter processes andperformance metrics for the individual and combinations of physicalresources. For example, an assessment of the performance of thedatacenter based on workloads, operating environment, operationsresources and physical resources can be used as a benchmark for settingminimum threshold limits for physical resources at the datacenter. Thebyproduct threshold manager 116 provides the threshold limits to beapplied to resource management. It is contemplated that the APIs providesupport for representing the minimum threshold data for performingevaluations with other representations in the resource managementsystem.

The byproduct resource manager 110 uses the resource managementframework including the API 114 and the byproduct threshold manager 116to quantify resources of the datacenter. The resources are physicalresources that are associated with the datacenter. The byproductresource manager 110 can quantify resources in two situations—fordevices and for requests. Quantifying resources can include generatingan instance. A device instance (e.g., device instance 140) can refer toa computed representation of a datacenter device in relation to aphysical resource and a reserve resource of the resource. An operationinstance (e.g., operation instance 150) can refer to an amount of aphysical resource needed to perform an anticipated operation. Someimplementations of resource management system 100 can operate optionallybased on requested units from a remote resource interface thatcommunicates the requested units for a physical resource. As discussedin more detail with reference to infrastructure management system inFIG. 8, the byproduct resource manager can receive device datacomprising requested units of a physical resource that is needed for ananticipated operation and then generate an operation instance to performresource management. As such, requests for physical resources can bereceived and processing in different way by different components of theresource management system. The device instance and the operationinstances can be used to determine allocable units of a resource. Thebyproduct resource manager can generate an instance for a device oroperation.

The byproduct resource manager 110 controls an amount of the physicalresource that is generated and an amount the physical resource that isreserved for a device from the plurality of devices. The byproductresource manager 120 controls the device based on the device instance.For example, for a device 102A, device 102A can produce power. Thedevice 102A can have a device instance that indicates physical resourcesassociated with the devices. The byproduct resource manager 110 cancommunicate operation instructions 124 to the plurality of byproductdevices 120 to control generating and reserving physical resourcesassociated with the byproduct devices. The byproduct resource manager110 in particular controls the amount of a physical resource that isgenerated and the amount of physical resource that is reserved based ona minimum threshold resource. It is contemplated that byproduct resourcemanager may communicate control such that any value or no value for anamount of a physical resource to be generated and amount of physicalresource to be reserved. Controls can be communicated dynamically basedon changes in the infrastructure. The minimum threshold units ofphysical resources can be accessed via the byproduct threshold manager116. The minimum threshold reserve in combination with the control overgenerating and reserving the physical resources help identify anallocable amount (e.g., allocable units 160) of the physical resource.An allocated amount (e.g., allocated units) of the allocable amount canbe communicated to the remote resource interface 130. In operation, theresource management system can support different types ofimplementations including—a datacenter byproduct management interfacesystem, a datacenter power management system, a datacenter operationsoptimization system, and an infrastructure resource management system.

Datacenter Byproduct Management System

With continued reference to FIG. 1, the datacenter 120A can support adatacenter byproduct management system. In operation, the byproductresource manager 110 is configured to receive byproduct device data 112for byproduct devices associated with the data 120. The byproductresource manager also generates, based on the byproduct device data, adevice instance (e.g., device instance 140) having a plurality ofattributes associated with the byproduct device. The device instanceincludes a generation capacity of units of a physical resource andreserve units of the physical resource. The device instance is acomputed representation of the byproduct device in relation to thephysical resource and a reserve of the physical resource, the deviceinstance supports determining allocable units (e.g., allocable units160) of the physical resource.

The byproduct resource manager 110 communicates operation instructionsto the byproduct device for an amount of units of the physical resourceto be generated and an amount of units of the physical resource to bereserved, based on the device instance and a minimum threshold reserveof the physical resource associated with operating the datacenter. Thebyproduct resource manager 110 automatically updates an amount ofallocable units of the physical resource based on an amount of units ofthe physical resource that is being generated and an amount of units ofthe physical resource that is reserved.

The physical resource to be generated is generated based on thebyproduct device producing the physical resource. As used herein,producing the physical resource can refer to transmitting the physicalresource from a generation source to be made available for consumptionvia the datacenter. Producing the physical resource can also be based onthe byproduct device throttling usage of the physical resource such thatan unused portion of the physical resource is made available forconsumption via the datacenter. Reserving the physical resource can bebased on an internal component (e.g., UPS battery) or an externalcomponent (e.g., independent batter cells) associated with the byproductdevice.

The remote resource interface 130 configured can generate a requesthaving requested units of the physical resource. The byproduct resourcemanager can receive the request and generate an operation instance forprocessing the request. The remote resource interface can then receivean amount of allocated units for the request based on an amount of unitsof the physical resource that is being generated and an amount of unitsof the physical resource that is reserved.

It is contemplated that the byproduct resource manager and the remoteresource interface can communicate corresponding notifications toactuate one or more physical devices within the datacenter and anoperating infrastructure providing an operating environment for remoteresource interface. The notification initiates operation processes forprocessing the amount of allocated units of the physical resource.

Turning now to FIG. 2, a flow diagram is provided that illustrates amethod 200 for providing resource management. Initially at block 210,byproduct device data is received for a byproduct device associated witha datacenter. The byproduct device data can be received based on an APIsthat are supported at the byproduct device data such that the data isprovided in based on protocols of the API. At block 220, a deviceinstance is generated based on the byproduct device data. The deviceinstance includes a plurality of attributes associated with thebyproduct device. The device instance includes a generation capacity ofunits of a physical resource and reserve units of the physical resource.The device instance is a computed representation of the byproduct devicein relation to the physical resource and a reserve of the physicalresource, the device instance supports determining allocable units ofthe physical resource.

At block 230, a request having requested units of the physical resourceis received. The request can be received from a remote resourceinterface. The request can be received based on APIs that are supportedat the remote resource interface such that the request is provided inbased on protocols of the API. Upon receiving the request, the byproductresource manager can communicate operation instructions to the byproductdevice for an amount of units of the physical resource to be generatedand an amount of units of the physical resource to be reserved, based atleast in part on the device instance and the minimum threshold reserveof the physical resource associated with the datacenter. An operationinstance can be generated, the operation instance comprising requestedunits that indicate an amount of a physical resource needed inanticipation of an operation. The physical resource being generated isgenerated based on the byproduct device throttling usage of the physicalresource such that an unused portion of the physical resource is madeavailable for consumption via the datacenter. Reserving the physicalresource is based on an internal component or an external componentassociated with the byproduct device. At block 240, an amount ofallocated units for the request based on an amount of units of thephysical resource that is being generated and an amount of units of thephysical resource that are reserved, is communicated. The amount ofunits of the physical resources being generated and the amount of unitsof the physical resource being reserved is based at least in part on thedevice instance and a minimum threshold reserve of the physical resourceassociated with operating the datacenter.

Turning now to FIG. 3, a flow diagram is provided that illustrates amethod 300 for providing resource management. Computer storage mediahaving computer-executable instructions embodied thereon that, whenexecuted, by one or more processors, causes the one or more processorsto perform the method for datacenter byproduct management. Initially atblock 310, a request having requested units of a physical resource isgenerated. The request is generated based on remote device data of aremote device that is associated with the physical resource. Thephysical resource is selected from one of the following: power, water,carbon dioxide and heat. At block 320, the request for the physicalresource is communicated to a byproduct resource manager; the byproductresource manager operates to generate device instances for byproductdevices. The device instances include a generation capacity of units ofa physical resource and reserve units of the physical resource. A deviceinstance is a computed representation of a byproduct device in relationto the physical resource and a reserve of the physical resource, thedevice instance supports determining allocable units of the physicalresource.

At block 330, an amount of allocated units of the physical resource forthe request based on an amount of units of the physical resource that isbeing generated and an amount of units of the physical resource that isreserved is received. The amount of units of the physical resourcesbeing generated and the amount of units of the physical resource beingreserved is based at least in part on the device instance and theminimum threshold reserve of the physical resource associated with thedatacenter. A notification to actuate one or more physical deviceswithin an operating infrastructure that is the operating environment ofthe remote device is communicated to initiate operation processes forthe processing the amount of allocated units of the physical resource.The operating infrastructure is selected from one of the following: apower grid, a co-located agricultural facility, a manufacturingfacility, a building, and a remote datacenter. The byproduct resourcemanager upon receiving the request communicates operation instructionsto the byproduct device for an amount of units of the physical resourceto be generated and the amount of units of the physical resource to bereserved, based on the device instance and the minimum threshold reserveof the physical resource associated with operating the datacenter.

Datacenter Power Management System

With reference to FIG. 4, embodiments of the present disclosure can bediscussed with reference to an exemplary implementation of the resourcemanagement system 100 as a datacenter power management system 400. Thepower management system 400 includes a power manager 410, a plurality ofdevices 420 (420A, 420B, 420C and 420D) and a remote resource interface430. The power manager 410 monitors power 412 of the plurality ofdevices 120 (e.g., power 426). The power manager 410 also includes anApplication Programming Interface 414 and a power threshold manager 216.The power management system is provided for leveraging power devices ina datacenter to support an electrical grid.

In operation, the power manager 410 receives power device data for apower device associated with the datacenter 420A. The use of datacenteris not meant to be limiting. Other types of infrastructure supporting aplurality of power devices that can be monitored as discussed herein arecontemplated. The power manager 410 can generate based on the powerdevice data 422, a device instance (e.g., power device instance 440)having a plurality of attributes associated with the power device, thedevice instance comprising a generation capacity of units of power andreserve units of power. The device instance is a computed representationof the power device in relation to power as a physical resource and areserve of power, the instance supports determining allocable units ofpower. The power manager 410 communicates operation instructions (e.g.,operation instructions 424) to the power device for an amount of unitsof power to be generated and an amount of units of power to be reserved,based on the device instance and a minimum threshold reserve of powerassociated with operating the datacenter.

The power manager 410 automatically updates an amount of allocable unitsof power based on an amount of units of power that is being generatedand an amount of units of power that is reserved. The power to begenerated is generated based on the power device producing power in partby transmitting power from a generation source to be made available forconsumption via the datacenter or the power device throttling usage ofpower such that an unused portion of power is made available forconsumption via the datacenter. The power to be reserved is reservedbased an internal component or an external component associated with thepower device.

The remote power interface 430 can generate a request (e.g., requestedunits 432) having requested units of power. The remote power interfacecan communicate the requested units 432 to receive allocated units(e.g., allocated units 434) of power from the power manager 410. Thepower manager can receive the request and generate an operation instance(e.g., operation instance 450) for processing the request. The remotepower interface receives an amount of allocated units for the requestbased on an amount of units of power that is being generated and anamount of units of power that is reserved. In particular, the amount ofunits of power that is being generated and an amount of units of powerthat is reserved in combination with the device instance 440 helpidentify an allocable amount (e.g., allocable units 460). A powermanagement scheme supports generating and reserving power based oncorresponding electrical components and electricity processingtechniques associated with the power device. The power manager 410 andthe remote power interface 430 can communicate correspondingnotifications to actuate one or more physical devices within thedatacenter and a power grid, respectively. The notifications initiateoperation processes for the processing the amount of allocated units ofpower.

Turning now to FIG. 5, a flow diagram is provided that illustrates amethod 500 for providing resource management. Initially at block 510,power device data for a power device associated with a datacenter isreceived. The power device data can be received based on an APIs thatare supported at the byproduct device data such that the data isprovided in based on protocols of the API. At block 520, a deviceinstance having a plurality of attributes associated with the powerdevice is generated based on the power device data. The device instanceincludes a generation capacity of units of power and reserve units ofpower. The device instance is a computed representation of the powerdevice in relation to power as a physical resource and a reserve ofpower, the device instance supports determining allocable units ofpower.

At block 530, a request having requested units of power is received. Therequest can be received from a remote power interface. Upon receivingthe request, the power manager can communicate operation instructions tothe power device for an amount of units of power to be generated and anamount of units of power to be reserved, based at least in part on thedevice instance and the minimum threshold reserve of the powerassociated with the datacenter. The power being generated is generatedbased on the power device throttling usage of the power such that anunused portion of the power is made available for consumption via thedatacenter. Reserving the power is based on an internal component or anexternal component associated with the byproduct device.

At block 540, an amount of allocated units for the request based on anamount of units of the power that is being generated and an amount ofunits of the power that is reserved is communicated. The amount of unitsof the power being generated and the amount of units of the power beingreserved is based at least in part on the device instance and a minimumthreshold reserve of the power associated with operating the datacenter.The power generated is based on an Application Programming Interfacethat supports a protocol for processing powers based on the power devicein relation to power and a reserve of power.

Turning now to FIG. 6, a flow diagram is provided that illustrates amethod 600 for providing resource management. Computer storage mediahaving computer-executable instructions embodied thereon that, whenexecuted, by one or more processors, causes the one or more processorsto perform the method for datacenter power management. Initially atblock 610, a request having requested units of a power is generated. Therequest is generated based on remote power device data of a remote powerdevice that is associated with the power. At block 620, the request forthe power is communicated to a power manager; the power manager operatesto generate power device instances for power devices. The deviceinstances include a generation capacity of units of a power and reserveunits of power. A device instance is a computed representation of apower device in relation to power and a reserve of the power, the deviceinstance supports determining allocable units of the power.

At block 630, an amount of allocated units of the power for the requestbased on an amount of units of the power that is being generated and anamount of units of the power that is reserved is received. The amount ofunits of the power being generated and the amount of units of the powerbeing reserved is based at least in part on the device instance and theminimum threshold reserve of the power associated with the datacenter. Anotification to actuate one or more physical devices within an operatinginfrastructure that is the operating environment of the remote device iscommunicated to initiate operation processes for the processing theamount of allocated units of the power. The power grid is a smart gridthat operates based on a grid connect system to opportunisticallybalance the power grid based on the datacenter power usage.

Datacenter Operations Optimization System

With reference to FIG. 7, embodiments of the present disclosure can bediscussed with reference to an exemplary implementation of the resourcemanagement system 100 as a datacenter operations optimization systemmanagement system 700. The datacenter operations optimization system 700includes a byproduct resource manager 710, a plurality of devices 720(720A, 720B, 720C and 720D) and a remote resource interface 730. Thebyproduct resource manager 110 monitors a plurality of byproducts 712(712A, 712B, 712C and 712D) of the plurality of devices 720 (e.g., 726A,726B, 726C and 726D). The byproduct resource manager 110 also includesan Application Programming Interface 714 and a byproduct thresholdmanager 716.

In operation, the byproduct resource manager 710 receives byproductdevice data (e.g., byproduct device data 722) for a plurality ofbyproduct devices (e.g., plurality of byproduct devices 720) associatedwith a datacenter 720A associated with a co-located operatinginfrastructure (e.g., 720B) that is an operating environment that sharesphysical resources with the datacenter. The datacenter 720A is shownwith greenhouse 720 as an exemplary co-located operating infrastructure.The byproduct resource manager is responsible for generating, based onthe byproduct device data, a plurality of device instances (e.g., deviceinstance 740) having a plurality of attributes associated with thebyproduct devices. The plurality of device instances includes ageneration capacity of units of one or more physical resources andreserve units of the one or more physical resources. A device instanceis a computed representation of the byproduct devices in relation to theone or more physical resources and a reserve of the one or more physicalresources, the device instance supports determining allocable units ofthe one or more physical resources.

The byproduct resource manager communicates operation instructions(e.g., operation instructions 724) to the byproduct devices for anamount of units of the one or more physical resources to be generatedand an amount of units of the one or more physical resources to bereserved, based on the plurality of device instances and a minimumthreshold reserve of the one or more physical resources associated withoperating the datacenter with the co-located operating infrastructure.The minimum threshold reserve can be retrieved from the byproductthreshold manager 716.

The byproduct resource manager 110 automatically updates an amount ofallocable units of the one or more physical resources based on an amountof the one or more physical resources that are being generated and anamount of units of the one or more physical resources that are reserved.The one or more physical resources to be generated are generated basedon the byproduct device producing the one or more physical resources. Aphysical resource can be produced by transmitting the physical resourcefrom a generation source to be made available for consumption via thedatacenter or the byproduct device throttling usage of the one or morephysical resources such that an unused portion of the one or morephysical resource is made available for consumption via the datacenter.Reserving the one or more physical resources is based on an internalcomponent or an external component associated with the byproduct devicesin the datacenter and co-located operating infrastructure.

The remote resource interface is responsible for generating a requesthaving requested units of the one or more physical resources. Thebyproduct resource manager can receive the request and generate anoperation instance (e.g., operation instance 750) for processing therequest. The remote resource interface 730 can communicate the requestedunits 732 to receive allocated units (e.g., allocated units 734) of theone or more physical resources from the byproduct resource manager 710.The remote resource interface 730 receives an amount of allocated unitsfor the request based on an amount of units of power that is beinggenerated and an amount of units of power that is reserved. Inparticular, the amount of units of power that is being generated and anamount of units of the one or more physical resources that is reservedin combination with the device instance 740 help identify an allocableamount (e.g., allocable units 760). The byproduct resource manager 710and the remote resource interface 730 can communicate correspondingnotifications to actuate one or more physical devices within thedatacenter and an operating environment for the remote resourceinterface, respectively. The notifications initiate operation processesfor the processing the amount of allocated units of the one or morephysical resources.

The remote datacenter manager of remote datacenter 730C is responsiblefor generating a request having requested units for compute resources.The remote datacenter manager can communicate the request to thebyproduct resource manager 710 (e.g., compute resource manager—notshown) in order to receive an amount of allocated units of computeresources based on an amount of units of the one or more physicalresources that are being generated and an amount of units of the one ormore physical resources that are reserved. The remote datacenter managercan transmit a compute workload to the datacenter to utilize the amountof allocated units of compute resources that are based on theavailability of physical resources at the datacenter.

Turning now to FIG. 8, a flow diagram is provided that illustrates amethod 800 for providing resource management. Initially at block 810,byproduct device data is received for a byproduct device associated witha datacenter and a co-located operating infrastructure. The co-locatedoperating infrastructure is an operating environment that sharesphysical resources with the datacenter. The byproduct device data can bereceived based on an APIs that are supported at the byproduct devicedata such that the data is provided in based on protocols of the API. Atblock 820, a device instance is generated based on the byproduct devicedata. The device instance includes a plurality of attributes associatedwith the byproduct device. The device instance includes a generationcapacity of units of one or more physical resource and reserve units ofthe physical resource. The device instance is a computed representationof the byproduct device in relation to the one or more physical resourceand a reserve of the one or more physical resource, the device instancesupports determining allocable units of the physical resource.

At block 830, a request having requested units of the physical resourceis received. The request can be received from a remote resourceinterface. The request can be received based on APIs that are supportedat the remote resource interface such that the request is provided inbased on protocols of the API. Upon receiving the request, the byproductresource manager can communicate operation instructions to the byproductdevice for an amount of units of the one or more physical resources tobe generated and an amount of units of the physical resource to bereserved, based at least in part on the device instance and the minimumthreshold reserve of the one or more physical resources associated withthe datacenter. The one or more physical resource being generated isgenerated based on the byproduct device throttling usage of the physicalresource such that an unused portion of the one or more physicalresource is made available for consumption via the datacenter. Reservingthe one or more physical resource is based on an internal component oran external component associated with the byproduct device.

At block 840, an amount of allocated units for the request based on anamount of units of the one or more physical resource that is beinggenerated and an amount of units of the physical resource that arereserved, is communicated. The amount of units of the one or morephysical resources being generated and the amount of units of thephysical resource being reserved is based at least in part on the deviceinstance and a minimum threshold reserve of the one or more physicalresource associated with operating the datacenter. The byproductresource manager automatically updates an amount of allocable units ofthe one or more physical resources based on an amount of the one or morephysical resources that are being generated and an amount of units ofthe one or more physical resources that are reserved.

Turning now to FIG. 9, a flow diagram is provided that illustrates amethod 900 for providing resource management. Computer storage mediahaving computer-executable instructions embodied thereon that, whenexecuted, by one or more processors, causes the one or more processorsto perform the method for datacenter byproduct management. Initially atblock 910, a request having requested units of one or more physicalresource is generated. The request is generated for one or more physicalresource from a datacenter associated with a co-located operatinginfrastructure that is an operating environment that shares physicalresource with the datacenter. The request is generated based on remotedevice data of a remote device that is associated with the one or morephysical resources. The physical resource is selected from one of thefollowing: power, water, carbon dioxide and heat. At block 920, therequest for the one or more physical resource is communicated to abyproduct resource manager; the byproduct resource manager operates togenerate a plurality of device instances for byproduct devices. Theplurality of device instances includes a generation capacity of units ofa physical resource and reserve units of the physical resource. A deviceinstance is a computed representation of a byproduct device in relationto the physical resource and a reserve of the physical resource, thedevice instance supports determining allocable units of the physicalresource.

At block 930, an amount of allocated units of the physical resource forthe request based on an amount of units of the one or more physicalresources that is being generated and an amount of units of the physicalresource that is reserved is received. The amount of units of thephysical resources being generated and the amount of units of the one ormore physical resource being reserved is based at least in part on thedevice instance and the minimum threshold reserve of the one or morephysical resources associated with the datacenter. A notification toactuate one or more physical devices within an operating infrastructurethat is the operating environment of the remote device is communicatedto initiate operation processes for the processing the amount ofallocated units of the physical resource. The operating infrastructureis selected from one of the following: a power grid, a co-locatedagricultural facility, a manufacturing facility, a building, and aremote datacenter. The byproduct resource manager upon receiving therequest communicates operation instructions to the byproduct device foran amount of units of the physical resource to be generated and theamount of units of the physical resource to be reserved, based on thedevice instance and the minimum threshold reserve of the physicalresource associated with operating the datacenter.

Infrastructure Management System

With reference to FIG. 10, embodiments of the present disclosure can bediscussed with reference to an exemplary implementation of the resourcemanagement system 100 as an infrastructure management system 1000. Theinfrastructure management system 1000 includes a byproduct resourcemanager 1010, a plurality of devices 1020 (1020A, 1020B, 1020C and1020D). The infrastructure devices can further be divided into 1030Aassociated with a requesting infrastructure device and 1030B associatedwith additional infrastructure devices. The byproduct resource manager110 monitors byproduct resources (e.g., 1012A, 1012B, 1012C and 1012D)of the plurality of devices 120 (e.g., 1026A, 1026B, 1026C and 1026D).The byproduct resource manager 1010 also includes an ApplicationProgramming Interface 1014 and a power threshold manager 1016.

In operation, the byproduct resource manager 1010 (or infrastructureresource manager) receives infrastructure device data (e.g.,infrastructure device data 1022) for an infrastructure device (e.g.,infrastructure device 1030) associated with a physical resource of aninfrastructure. The infrastructure (e.g., infrastructure 1020A) can beselected form one of the following: a power grid, a co-locatedagricultural facility, a manufacturing facility, a building, and aremote datacenter. An operation instance (e.g., operation instance 1050)is generated based on the infrastructure device data. The operationinstance includes a plurality of attributes associated with theinfrastructure device. The operation instance also includes requestedunits that indicate an amount of a physical resource is needed toperform an infrastructure device operation. The byproduct resourcemanager 1010 communicates operation instructions (e.g., operationinstructions 1024) to one or more additional infrastructure devices(e.g., additional infrastructure devices 1030B) for an amount of unitsof the physical resource to be generated and an amount of units of thephysical resource to be reserved. The operating instructions are basedon the operation instance and a minimum threshold reserve of thephysical resource associated with operating the infrastructure. Thebyproduct resource manager 1010 determines an amount of allocable units(e.g., allocable units 1060) and an amount of allocated units of thephysical resource based in part on the operation instance and an amountof units of the physical resource that is being generated and the amountof units of the physical resource that is reserved and then communicatesoperation instructions (e.g., operation instructions 1032) to theinfrastructure device. The operation instructions include the amount ofallocated units of the physical resource. The byproduct resource managermay be responsible to generate, based on the infrastructure device data,a device instance (e.g., device instance 1040) having a plurality ofattributes associated with the infrastructure device, the deviceinstance comprising a generation capacity of units of a physicalresource and reserve units of the physical resource, wherein the deviceinstance is a computed representation of the byproduct device inrelation to the physical resource and a reserve of the physicalresource, the device instance supports determining allocable units ofthe physical resource.

The infrastructure resource manager automatically updates an amount ofallocable units of the physical resource based on the amount of units ofthe physical resource that is being generated and an amount of units ofthe physical resource that is reserved. The physical resource to begenerated is generated based on the one or more additionalinfrastructure devices producing the physical resource in part bytransmitting the physical resource from a generation source to be madeavailable for consumption via the datacenter or the one or moreadditional infrastructure devices throttling usage of the physicalresource such that an unused portion of the physical resource is madeavailable for consumption via the datacenter.

An infrastructure device is configured to communicate the infrastructuredevice data that is used in determining the amount of the requestedphysical resource units need for the anticipated infrastructure deviceoperation, receive the amount of allocated units for the infrastructuredevice operation; and initiate processing of the amount of allocatedunits for the performing the infrastructure device operation. By way ofexample, the infrastructure device is an electrical appliance that isassociated with the infrastructure operating as a building facility andthe one or more additional infrastructures device are computing deviceswithin the building. In another example, the infrastructure device is anelectrical grid device that is associated with the infrastructureoperating based on an electric grid, a grid connector, and a datacenter,and the one or more additional infrastructure devices are power devicesin the datacenter.

As discussed with reference to datacenter optimization operationssystem, the infrastructure management system can further include supporta remote datacenter manager that is responsible for generating a requesthaving requested units for compute resources. The remote datacentermanager can communicate the request to the byproduct resource manager1010 (e.g., compute resource manager—not shown) in order to receive anamount of allocated units of compute resources based on an amount ofunits of the one or more physical resources that are being generated andan amount of units of the one or more physical resources that arereserved. The remote datacenter manager can transmit a compute workloadto the datacenter to utilize the amount of allocated units of computeresources that are based on the availability of physical resources atthe datacenter.

Turning now to FIG. 11, a flow diagram is provided that illustrates amethod 500 for providing resource management. Initially at block 1110,infrastructure data for an infrastructure device associated with aphysical resource is received. At block 1120, an operation instancehaving a plurality of attributes associated with the infrastructuredevice is generated. The operation instance includes requested unitsthat indicate an amount of a physical resource needed in anticipation ofan infrastructure device operation. At block 1130, operationinstructions are communicated to one or more additional infrastructuredevices an amount of units of the physical resource to be generated andan amount of units of the physical resource to be reserved, based on theoperation instance and a minimum threshold reserve of the physicalresource associated with operating the one or more additionalinfrastructure devices.

At block 1140, an amount of allocated units of the physical resources isdetermined based in part on the instance and an amount of units of thephysical resource that is being generated and the amount of units of thephysical resource that is reserved. The physical resource beinggenerated is generated based on the byproduct device producing thephysical resource in part by transmitting the physical resource from ageneration source to be made available for consumption via thedatacenter. In the alternative, the physical resource being generated isgenerated based on the byproduct device throttling usage of the physicalresource such that an unused portion of the physical resource is madeavailable for consumption via the datacenter. At block 1150, operationinstructions to the infrastructure device are communicated. Theoperation instructions include the amount of allocated units of thephysical resource. A notification to actuate one or more physicaldevices within the infrastructure is communicated to initiate operationprocesses for processing the amount of allocated units of the physicalresource.

Turning now to FIG. 12 a flow diagram is provided that illustrates amethod 1200 for resource management. Computer storage media havingcomputer-executable instructions embodied thereon that, when executed,by one or more processors, causes the one or more processors to performthe method for datacenter power management. Initially at block 1210,infrastructure device data is communicated to an infrastructure resourcemanager. The infrastructure resource manager generates operationinstances having a plurality of attributes associated with theinfrastructure device, the operation instance comprising requestedphysical resource units that indicate an amount of a physical resourceneeded in anticipation of an infrastructure device operation. At block1220, an amount of allocated units for the infrastructure deviceoperation is received. The amount of allocated units are generated basedin part on the operation instance and an amount of units of the physicalresource that is being generated and the amount of units of the physicalresource that is reserved. At block 1230, processing of the amount ofallocated units is initiated for the performing the infrastructuredevice operation.

Computing Environments and Context

Having identified various components of the distributed computingenvironments in FIGS. 1, 4, 7 and 10, it is noted that any number ofcomponents may be employed to achieve the desired functionality withinthe scope of the present disclosure. The various components of FIGS. 1,4, 7 and 10 are shown with lines for the sake of clarity. Further,although some components of FIGS. 1, 4, 7 and 10 are depicted as singlecomponents, the depictions are exemplary in nature and in number and arenot to be construed as limiting for all implementations of the presentdisclosure. The configuration management system functionality can befurther described based on the functionality and features of theabove-listed components.

Other arrangements and elements (e.g., machines, interfaces, functions,orders, and groupings of functions, etc.) can be used in addition to orinstead of those shown, and some elements may be omitted altogether.Further, many of the elements described herein are functional entitiesthat may be implemented as discrete or distributed components or inconjunction with other components, and in any suitable combination andlocation. Various functions described herein as being performed by oneor more entities may be carried out by hardware, firmware, and/orsoftware. For instance, various functions may be carried out by aprocessor executing instructions stored in memory.

With further reference to the resource management system, embodimentsdescribed herein can improve datacenter operations based on a resourcemanagement framework. The integrated components of the resourcemanagement framework refer to the hardware architecture and softwareframework that support functionality using the fiber optic cable networktesting. The hardware architecture refers to physical components andinterrelationships thereof and the software framework refers to softwareproviding functionality that can be implemented with hardware operatedon a device. The end-to-end software-based resource management frameworkcan operate within the resource management system components to operatecomputer hardware to provide functionality described herein. As such,the components can manage resources and provide services for theresource management functionality. Any other variations and combinationsthereof are contemplated with embodiments of the present invention.

By way of example, the resource management framework can include an APIlibrary that includes specifications for routines, data structures,object classes, and variables may support the interaction the hardwarearchitecture of the device and the software framework of the testingplatform. These APIs include configuration specifications for theresource management system such that the components therein cancommunicate with each other, as described herein.

Having briefly described an overview of embodiments of the presentinvention, an exemplary operating environment in which embodiments ofthe present invention may be implemented is described below in order toprovide a general context for various aspects of the present invention.Referring initially to FIG. 13 in particular, an exemplary operatingenvironment for implementing embodiments of the present invention isshown and designated generally as computing device 1300. Computingdevice 1300 is but one example of a suitable computing environment andis not intended to suggest any limitation as to the scope of use orfunctionality of the invention. Neither should the computing device 1300be interpreted as having any dependency or requirement relating to anyone or combination of components illustrated.

The invention may be described in the general context of computer codeor machine-useable instructions, including computer-executableinstructions such as program modules, being executed by a computer orother machine, such as a personal data assistant or other handhelddevice. Generally, program modules including routines, programs,objects, components, data structures, etc. refer to code that performparticular tasks or implement particular abstract data types. Theinvention may be practiced in a variety of system configurations,including hand-held devices, consumer electronics, general-purposecomputers, more specialty computing devices, etc. The invention may alsobe practiced in distributed computing environments where tasks areperformed by remote-processing devices that are linked through acommunications network.

With reference to FIG. 13, computing device 1300 includes a bus 1310that directly or indirectly couples the following devices: memory 1312,one or more processors 1314, one or more presentation components 1316,input/output ports 1318, input/output components 1320, and anillustrative power supply 1322. Bus 1310 represents what may be one ormore busses (such as an address bus, data bus, or combination thereof).Although the various blocks of FIG. 13 are shown with lines for the sakeof clarity, in reality, delineating various components is not so clear,and metaphorically, the lines would more accurately be grey and fuzzy.For example, one may consider a presentation component such as a displaydevice to be an I/O component. Also, processors have memory. Werecognize that such is the nature of the art, and reiterate that thediagram of FIG. 13 is merely illustrative of an exemplary computingdevice that can be used in connection with one or more embodiments ofthe present invention. Distinction is not made between such categoriesas “workstation,” “server,” “laptop,” “hand-held device,” etc., as allare contemplated within the scope of FIG. 13 and reference to “computingdevice.”

Computing device 1300 typically includes a variety of computer-readablemedia. Computer-readable media can be any available media that can beaccessed by computing device 1300 and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable media may comprise computerstorage media and communication media.

Computer storage media include volatile and nonvolatile, removable andnon-removable media implemented in any method or technology for storageof information such as computer-readable instructions, data structures,program modules or other data. Computer storage media includes, but isnot limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disks (DVD) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or any other medium which can be used tostore the desired information and which can be accessed by computingdevice 100. Computer storage media excludes signals per se.

Communication media typically embodies computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of any ofthe above should also be included within the scope of computer-readablemedia.

Memory 1312 includes computer storage media in the form of volatileand/or nonvolatile memory. The memory may be removable, non-removable,or a combination thereof. Exemplary hardware devices include solid-statememory, hard drives, optical-disc drives, etc. Computing device 1300includes one or more processors that read data from various entitiessuch as memory 1312 or I/O components 1320. Presentation component(s)1316 present data indications to a user or other device. Exemplarypresentation components include a display device, speaker, printingcomponent, vibrating component, etc.

I/O ports 1318 allow computing device 1300 to be logically coupled toother devices including I/O components 1320, some of which may be builtin. Illustrative components include a microphone, joystick, game pad,satellite dish, scanner, printer, wireless device, etc.

Referring now to FIG. 14, FIG. 14 illustrates an exemplary distributedcomputing environment 1400 in which implementations of the presentdisclosure may be employed. In particular, FIG. 14 shows a high levelarchitecture of the replicable differential store platform system(“system”) comprising a cloud computing platform 1410, where the systemsupports optimizing database transactions. It should be understood thatthis and other arrangements described herein are set forth only asexamples. Other arrangements and elements (e.g., machines, interfaces,functions, orders, and groupings of functions, etc.) can be used inaddition to or instead of those shown, and some elements may be omittedaltogether. Further, many of the elements described herein arefunctional entities that may be implemented as discrete or distributedcomponents or in conjunction with other components, and in any suitablecombination and location. Various functions described herein as beingperformed by one or more entities may be carried out by hardware,firmware, and/or software. For instance, various functions may becarried out by a processor executing instructions stored in memory.

Data centers can support the distributed computing environment 1400 thatincludes the cloud computing platform 1410, rack 1420, and node 1430(e.g., computing devices, processing units, or blades) in rack 1420. Thesystem can be implemented with a cloud computing platform 1410 that runscloud services across different data centers and geographic regions. Thecloud computing platform 1410 can implement a fabric controller 1440component for provisioning and managing resource allocation, deployment,upgrade, and management of cloud services. Typically, the cloudcomputing platform 1410 acts to store data or run service applicationsin a distributed manner. The cloud computing infrastructure 1410 in adata center can be configured to host and support operation of endpointsof a particular service application. The cloud computing infrastructure1410 may be a public cloud, a private cloud, or a dedicated cloud.

The node 1430 can be provisioned with a host 1450 (e.g., operatingsystem or runtime environment) running a defined software stack on thenode 130. Node 1430 can also be configured to perform specializedfunctionality (e.g., compute nodes or storage nodes) within the cloudcomputing platform 1410. The node 1430 is allocated to run one or moreportions of a service application of a tenant. A tenant can refer to acustomer utilizing resources of the cloud computing platform 1410.Service application components of the cloud computing platform 1410 thatsupport a particular tenant can be referred to as a tenantinfrastructure or tenancy. The terms service application, application,or service are used interchangeably herein and broadly refer to anysoftware, or portions of software, that run on top of, or access storageand compute device locations within, a datacenter.

When more than one separate service application is being supported bythe nodes 1430, the nodes may be partitioned into virtual machines(e.g., virtual machine 1452 and virtual machine 1454). Physical machinescan also concurrently run separate service applications. The virtualmachines or physical machines can be configured as individualizedcomputing environments that are supported by resources 1460 (e.g.,hardware resources and software resources) in the cloud computingplatform 1410. It is contemplated that resources can be configured forspecific service applications. Further, each service application may bedivided into functional portions such that each functional portion isable to run on a separate virtual machine. In the cloud computingplatform 1410, multiple servers may be used to run service applicationsand perform data storage operations in a cluster. In particular, theservers may perform data operations independently but exposed as asingle device referred to as a cluster. Each server in the cluster canbe implemented as a node.

Client device 1480 may be linked to a service application in the cloudcomputing platform 1410. The client device 1480 may be any type ofcomputing device, which may correspond to computing device 1000described with reference to FIG. 14, for example. The client device 1480can be configured to issue commands to cloud computing platform 1410. Inembodiments, client device 1480 may communicate with serviceapplications through a virtual Internet Protocol (IP) and load balanceror other means that directs communication requests to designatedendpoints in the cloud computing platform 1410. The components of cloudcomputing platform 1410 may communicate with each other over a network(not shown), which may include, without limitation, one or more localarea networks (LANs) and/or wide area networks (WANs).

Having described various aspects of the distributed computingenvironment 1400 and cloud computing platform 1410, it is noted that anynumber of components may be employed to achieve the desiredfunctionality within the scope of the present disclosure. Although thevarious components of FIG. 14 are shown with lines for the sake ofclarity, in reality, delineating various components is not so clear, andmetaphorically, the lines may more accurately be grey or fuzzy. Further,although some components of FIG. 14 are depicted as single components,the depictions are exemplary in nature and in number and are not to beconstrued as limiting for all implementations of the present disclosure.

The subject matter of embodiments of the disclosure is described withspecificity herein to meet statutory requirements. However, thedescription itself is not intended to limit the scope of this patent.Rather, the inventors have contemplated that the claimed subject mattermight also be embodied in other ways, to include different steps orcombinations of steps similar to the ones described in this document, inconjunction with other present or future technologies. Moreover,although the terms “step” and/or “block” may be used herein to connotedifferent elements of methods employed, the terms should not beinterpreted as implying any particular order among or between varioussteps herein disclosed unless and except when the order of individualsteps is explicitly described.

Embodiments described herein may be combined with one or more of thespecifically described alternatives. In particular, an embodiment thatis claimed may contain a reference, in the alternative, to more than oneother embodiment. The embodiment that is claimed may specify a furtherlimitation of the subject matter claimed.

For detailed discussion purposes, the resource management system 100 isdescribed as a mechanism associated with an infrastructure (e.g.,datacenter 120A running the plurality of devices 120). A mechanism asused herein refers to any device, process, or service or combinationthereof. A mechanism may be implemented using components as hardware,software, firmware, a special-purpose device, or any combinationthereof. A mechanism may be integrated into a single device or it may bedistributed over multiple devices. The various components of a mechanismmay be co-located or distributed. The mechanism may be formed from othermechanisms and components thereof. The components of the resourcemanagement system 100 facilitate providing functionality describedherein.

For purposes of a detailed discussion above, embodiments are describedwith reference to distributed computing devices, components, and aresource management system components. Components can be configured toperform novel aspects of embodiments described herein, where “configuredto” includes components that are programmed to perform particular tasksor implement particular abstract data types using computer code. It iscontemplated that the methods described herein can be performed indifferent types of operating environments having alternateconfigurations of the functional components described herein. As such,the embodiments described herein are merely exemplary, and it iscontemplated that the techniques may be extended to other implementationcontexts.

For purposes of this disclosure, the word “including” has the same broadmeaning as the word “comprising,” and the word “accessing” involves“receiving,” “referencing,” or “retrieving.” In addition, words such as“a” and “an,” unless otherwise indicated to the contrary, include theplural as well as the singular. Further the word “communicating” has thesame broad meaning as the word “receiving,” or “transmitting”facilitated by software or hardware-based buses, receivers, ortransmitters” using communication media described herein. Thus, forexample, the constraint of “a feature” is satisfied where one or morefeatures are present. Also, the term “or” includes the conjunctive, thedisjunctive, and both (a or b thus includes either a or b, as well as aand b).

Embodiments presented herein have been described in relation toparticular embodiments which are intended in all respects to beillustrative rather than restrictive. Alternative embodiments willbecome apparent to those of ordinary skill in the art to which thepresent invention pertains without departing from its scope.

From the foregoing, it will be seen that this invention is one welladapted to attain all the ends and objects hereinabove set forthtogether with other advantages which are obvious and which are inherentto the structure.

It will be understood that certain features and sub-combinations are ofutility and may be employed without reference to other features orsub-combinations. This is contemplated by and is within the scope of theclaims.

The invention claimed is:
 1. A datacenter power management system, thesystem comprising: a power manager configured to: receive power devicedata for a power device associated with a datacenter; generate, based onthe power device data, a device instance having a plurality ofattributes associated with the power device, the device instancecomprising a generation capacity of units of power and reserve units ofpower, wherein the device instance is a computed representation of thepower device in relation to power as a physical resource and a reserveof power, the device instance supports determining allocable units ofpower; and communicate operation instructions to the power device for anamount of units of power to be generated and an amount of units of powerto be reserved, based on the device instance and a minimum thresholdreserve of power associated with operating the datacenter.
 2. The systemof claim 1, wherein the power manager automatically updates an amount ofallocable units of power based on an amount of units of power that isbeing generated and an amount of units of power that is reserved.
 3. Thesystem of claim 1, wherein power to be generated is generated based onthe power device producing power in part by transmitting power from ageneration source to be made available for consumption via thedatacenter or the power device throttling usage of power such that anunused portion of power is made available for consumption via thedatacenter.
 4. The system of claim 1, further comprising the powermanager configured to generate an operation instance, the operationinstance comprising requested units that indicate an amount of aphysical resource needed in anticipation of an operation.
 5. The systemof claim 1, further comprising: a remote power interface configured to:generate a request having requested units of power; and receive anamount of allocated units for the request based on an amount of units ofpower that is being generated and an amount of units of power that isreserved.
 6. The system of claim 1, further comprising: the powermanager and a remote power interface configured to: communicatecorresponding notifications to actuate one or more physical deviceswithin the datacenter and a power grid, respectively, to initiateoperation processes for the processing the amount of allocated units ofpower.
 7. The system of claim 1, wherein a power management schemesupports generating and reserving power based on correspondingelectrical devices and electricity processing techniques associated withthe power device.
 8. A computer-implemented method for using adatacenter power management system to provide power grid management, themethod comprising: receiving power device data for a power deviceassociated with a datacenter; generating, based on the power devicedata, a device instance having a plurality of attributes associated withthe power device, the device instance comprising a generation capacityof units of power and reserve units of power, wherein the instance is acomputed representation of the power device in relation to power as aphysical resource and a reserve of power, the device instance supportsdetermining allocable units of power; receiving, from a remote powerinterface, a request having requested units of power; and communicatingto the remote power interface an amount of allocated units for therequest based on an amount of units of power that is being generated andan amount of units of power that is reserved, wherein the amount ofunits of powers being generated and the amount of units of power beingreserved is based at least in part on the device instance and a minimumthreshold reserve of power associated with operating the datacenter. 9.The method of claim 8, further comprising automatically updating anamount of allocable units of power based on the amount of units of powerthat is being generated and the amount of units of power that isreserved.
 10. The method of claim 8, further comprising, upon receivingthe request, communicating operation instructions to the power devicefor an amount of units of power to be generated and an amount of unitsof power to be reserved, based at least in part on the device instanceand the minimum threshold reserve of power associated with thedatacenter.
 11. The method of claim 8, wherein power being generated isgenerated based on the power device producing power in part bytransmitting power from a generation source to be made available forconsumption via the datacenter.
 12. The method of claim 8, wherein powerbeing generated is generated based on the power device throttling usageof power such that an unused portion of power is made available forconsumption via the datacenter.
 13. The method of claim 8, furthercomprising generating an operation instance, the operation instancecomprising requested units that indicate an amount of a physicalresource needed in anticipation of an operation.
 14. The method of claim8, further comprising communicating a notification to actuate one ormore physical devices within the datacenter to initiate operationprocesses for processing the amount of allocated units of power.
 15. Themethod of claim 8, wherein generating power is based on an ApplicationProgramming Interface that supports a protocol for processing powersbased on the power device in relation to power and a reserve of power.16. A computer-implemented method for datacenter power management,comprising: generating, at a remote power interface, a request havingrequested units of power; communicating the request for power to a powermanager, the power manager generates device instances for power devices,the device instances comprising a generation capacity of units of powerand reserve units of power, wherein a device instance is a computedrepresentation of a power device in relation to power and a reserve ofpower, the device instance supports determining allocable units ofpower; and receiving an amount of allocated units of power for therequest based on an amount of units of power that is being generated andan amount of units of power that is reserved, wherein the amount ofunits of powers being generated and the amount of units of power beingreserved is based at least in part on the device instance and theminimum threshold reserve of power associated with the datacenter. 17.The method of claim 16, wherein the request is generated based on remotepower device data of a remote power device that is associated withpower.
 18. The method of claim 16, further comprising communicating anotification to actuate one or more physical devices within a power gridthat is an operating environment of the remote power device, to initiateoperation processes for the processing the amount of allocated units ofpower.
 19. The method of claim 18, wherein the power grid is a smartgrid that operates based on a grid connect system to opportunisticallybalance the power grid based on the datacenter power usage.
 20. Themethod of claim 16, wherein the power manager upon receiving the requestcommunicates operation instructions to the power device for an amount ofunits of power to be generated and the amount of units of power to bereserved, based on the instance and the minimum threshold reserve ofpower associated with operating the datacenter.